The following is a list of guidelines that must be considered when making MVS models that will be output as 3D PDF files using the C Tech 3D PDF Converter.
MVS output from write_VRML. You must follow the guidelines in write_VRML in addition to these additional guidelines.
Let's begin by building a simple application
Whose output is:
The first things we MUST do for VRML output are to remove the Legend and use an Unlocked Background. If you see a gradient background in your Viewer, you definitely aren't using an unlocked background. Once you use an unlocked background, you can still set a solid (single) background color.
Always set your Viewer to a Top View (180 Azimuth and 90 Elevation) before writing the VRML file.
If we output this current model as VRML and convert to 3D PDF,
the results are less than wonderful:
The above 3D PDF has three obvious problems:
We need to modify the application using two texture_colors modules as follows:
You'll notice that in the revised application, the output in the Viewer is virtually identical. This will address the first two problems, however we expect to resolve the dark borings in an upcoming release.
If we export this model to VRML and convert to PDF, the result is:
One other issue is that by default, we create isolines coincident with the surface(s) and resolve the coincidence in EVS using jitter. At some rotations you will notice that the isolines may disappear. This can be because jitter is not supported, but also because the underlying surface is so bright that the lines are not distinguishable.
This can be addressed using the surface_offset parameter in isolines. This will offset the lines from teh surface (in one direction) and eliminate the coincidence. However, this will also mean that the lines will not be visible from one side of the slice. Making the lines uncolored is another option.
© 1994-2018 ctech.com